home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000467_news@columbia.edu_Mon Dec 12 01:35:51 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA20867
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 17 Dec 1994 12:59:43 -0500
Received: by apakabar.cc.columbia.edu id AA23240
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 17 Dec 1994 12:59:42 -0500
Path: news.columbia.edu!panix!bloom-beacon.mit.edu!gatech!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: term type in telnet-macro (Kermit 3.14)
Message-Id: <1994Dec12.073551.35191@cc.usu.edu>
Date: 12 Dec 94 07:35:51 MDT
References: <3bul2u$47d@infosrv.rz.unibw-muenchen.de>
Organization: Utah State University
Lines: 48
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3bul2u$47d@infosrv.rz.unibw-muenchen.de>, p41bsmk@kommsrv.rz.unibw-muenchen.de (Peter Schmolck) writes:
> I'm using MS-Kermit 3.14 Beta-14. My UNIX-hosts do not know what to do
> with "vt320", and when trying to adjust my mscustom.ini definitions I
> noted an inconsistency (or bug?).
>
> The telnet macro in mskermit.ini:
>
> define TELNET -
> set flow none,-
> set port tcp \%1 \%2,-
> pause 0, if fail end 1,-
> if def \%3 set term type \%3,-
> if succ c
>
> and accordingly the myhost define in mscustom.ini:
>
> define myhost -
> telnet myhost 23 vt320,-
> if success assign myhost telnet \v(session)
>
> set the terminal type, and not only the TELNET-negotiated "telnet
> term-type" (which I rather preferred the macro to do). When I changed the
> myhost define from vt320 to vt220 the result was, that -- expectedly --
> the status line entry changed to VT220, but --unexpectedly-- the remote
> TELNET server still received a "VT320". (??)
>
> BTW, mskermit.bwr says: "... to create an override string with command
> SET TCP/IP TELNET-TERM-TYPE."
> ^^^^^^^^^^^^^^
> Instead this should read either "set tcp/ip term-type" or "set telnet
> term-type".
-----------
It's not your fault, it's ours.
In reality the MSK command SET PORT TCP/IP acquires just two
arguments: host and port number. It doesn't look for a terminal type.
The way to use a different terminal type is SET TERMINAL TYPE kind
or just SET TERMINAL kind. This will pass along to the host, upon
request, the same terminal type spelling we see in commands. Here is
the canned list, lifted from the code:
"UNKNOWN","H-19","VT52","VT100","VT102","VT220","VT320",
"TEK4014","VIP7809","PT200","D463","D470","wyse50","ANSI"
As you point out, the program uses SET TCP/IP TERM-TYPE ident
as the way to tell the host a different identication string than the
default method.
The docs will be modified to be clear and correct on both items.
Thanks,
Joe D.